Fixes #84

Summary

The C# release workflow was version-bumped, tagged, and pushed for csharp-v2.4.0, but dotnet nuget push returned HTTP 403 mid-flight, so clink on NuGet stayed at 2.3.0 and no GitHub release was created. The next push to main short-circuited on the pre-existing tag + version commit and never retried.

This PR ports the self-healing release pattern from js-ai-driven-development-pipeline-template to C# and rewires csharp.yml to resume mid-failed releases on the next push to main, without requiring a new changeset.

Root cause

• Every publish/verify/release step gated only on steps.version.outputs.version_committed == 'true'.
• version-and-commit.mjs returns already_released=true when the bumped tag already exists, so version_committed is 'false' on every retry after the first run pushed the tag.
• There was no idempotent probe of the NuGet flat-container index or the GitHub Releases endpoint.
• NUGET_API_KEY was never validated upfront; the expired key only surfaced mid-dotnet nuget push.

Full timeline, evidence captures, and template comparison are in docs/case-studies/issue-84/README.md (added in commit 7f2be75).

Changes

csharp/scripts/check-release-needed.mjs (new)

Pure decide() function plus async probes:

• https://api.nuget.org/v3-flatcontainer/{id-lower}/index.json for the csproj <Version> (returns null on 404).
• GET /repos/{owner}/{repo}/releases/tags/csharp-v{version} for the matching GitHub release.

Outputs to GITHUB_OUTPUT: should_release, skip_bump, current_version, nuget_published, github_release_exists, reason. Supports NUGET_INDEX_URL / GITHUB_API_URL overrides for tests.

.github/workflows/csharp.yml

• Inserted "Check if release is needed" step between changeset detection and version-and-commit.
• Inserted "Validate NuGet API key" upfront, with Resolve release version so downstream steps see the right <Version> even on self-healing reruns.
• Rewrote 5 release-job and 4 instant-release if: conditions to the union:

  if: >-
    steps.version.outputs.version_committed == 'true' ||
    steps.version.outputs.already_released == 'true' ||
    (steps.check_release.outputs.should_release == 'true' &&
     steps.check_release.outputs.skip_bump == 'true')

• Verify package on NuGet and Create GitHub Release now read steps.release_version.outputs.version so self-healing reruns publish the correct artifact.

Tests

• csharp/scripts/release-scripts.test.mjs: 8 new tests covering the pure decide() function, csproj parsing, and the CLI end-to-end via a 127.0.0.1 mock HTTP server for NuGet + GitHub probes. 12 tests total, all pass (~700ms).
• js/test/repositoryLayout.test.mjs: new regression guard asserting the self-healing gates remain in csharp.yml — the "Check if release is needed" step, check-release-needed.mjs invocation, at least 4 should_release && skip_bump gates, and at least 5 already_released gates. 21 tests total, all pass.

Cleanup

• Removed the stray root .gitkeep that violated the existing repositoryLayout test.

Upstream report

The same defect class is present in csharp-ai-driven-development-pipeline-template — filed issue #11 with the same diagnosis and a pointer back to this PR.

Test plan

• node --test js/test/*.test.mjs csharp/scripts/*.test.mjs → 21/21 pass locally.
• python3 -c "import yaml; yaml.safe_load(open('.github/workflows/csharp.yml'))" → valid YAML.
• Reviewed gh pr diff 85 for unintended deletions — only the narrow if: conditions and the broadened execFile import.
• CI green on the PR.
• After merge: next push to main triggers the workflow; check-release-needed correctly reports clink@2.4.0 already on NuGet (once the manual republish or self-heal lands) and short-circuits — or, if 2.4.0 is still missing, it resumes the publish + GitHub release without a new changeset.

References

• Case study: docs/case-studies/issue-84/README.md
• JS template reference: https://github.com/link-foundation/js-ai-driven-development-pipeline-template/blob/main/scripts/check-release-needed.mjs
• Upstream issue: Release workflow does not self-heal when NuGet publish fails after version commit + tag csharp-ai-driven-development-pipeline-template#11
• Cross-reference: Release job silently skips when PRs merge without changesets — unreleased fixes accumulate js-ai-driven-development-pipeline-template#36 documents the same defect class.